UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

SQL Server must identify potential security-relevant error conditions.


Overview

Finding ID Version Rule ID IA Controls Severity
V-40906 SQL2-00-022700 SV-53260r2_rule Medium
Description
The structure and content of SQL Server error messages need to be carefully considered by the organization and development team. The extent to which the application is able to identify and handle error conditions is guided by organizational policy and operational requirements. Database logs can be monitored for specific security-related errors. Any error that can have a negative effect on database security should be quickly identified and forwarded to the appropriate personnel. If security-relevant error conditions are not identified by SQL Server they may be overlooked by the personnel responsible for addressing them.
STIG Date
Microsoft SQL Server 2012 Database Instance Security Technical Implementation Guide 2017-12-01

Details

Check Text ( C-47561r2_chk )
Security-related errors must be identified and monitored. In most cases, these items would appear in the SQL Server log file.

If security-related error conditions are not being monitored to meet this requirement, this is a finding.
Fix Text (F-46188r2_fix)
Monitor SQL Server log files to determine when a security-related error occurs.

Add/Update list of appropriate personnel that are to be alerted when a security related error condition occurs to system documentation. Consider an automated job for both the monitor and the alerting.